Methods and Systems for Protecting a Secured Network

ABSTRACT

Methods and systems for protecting a secured network are presented. For example, one or more packet security gateways may be associated with a security policy management server. At each packet security gateway, a dynamic security policy may be received from the security policy management server, packets associated with a network protected by the packet security gateway may be received, and at least one of multiple packet transformation functions specified by the dynamic security policy may be performed on the packets.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 14/253,992 (now U.S. Pat. No. 9,565,213), filedApr. 16, 2014, and entitled “METHODS AND SYSTEMS FOR PROTECTING ASECURED NETWORK,” the disclosure of which is incorporated by referenceherein in its entirety.

BACKGROUND

The TCP/IP network protocols (e.g., the Transmission Control Protocol(TCP) and the Internet Protocol (IP)) were designed to build large,resilient, reliable, and robust networks. Such protocols, however, werenot originally designed with security in mind. Subsequent developmentshave extended such protocols to provide for secure communication betweenpeers (e.g., Internet Protocol Security (IPsec)), but the networksthemselves remain vulnerable to attack (e.g., Distributed Denial ofService (DDoS) attacks).

Most existing approaches to protecting such networks are reactive ratherthan proactive. While reactive approaches may identify the source of anattack and assist in subsequent mitigation efforts, in most instances,the attack will have already been successfully launched.

Proactive solutions, however, have often been deemed untenable due to aninability to scale to larger networks. A significant challengeassociated with building a scalable proactive solution is the need tofilter substantially all network traffic at a high resolution. In alarge network, where traffic volumes may be enormous, the time requiredto provide high resolution filtering has traditionally been thought torender a proactive solution infeasible.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects of the disclosure. It is neither intendedto identify key or critical elements of the disclosure nor to delineatethe scope of the disclosure. The following summary merely presents someconcepts in a simplified form as a prelude to the description below.

Aspects of this disclosure relate to protecting a secured network. Insome embodiments, one or more packet security gateways are associatedwith a security policy management server. At each of the packet securitygateways, a dynamic security policy may be received from the securitypolicy management server, packets associated with a network protected bythe packet security gateway may be received, and at least one ofmultiple packet transformation functions specified by the dynamicsecurity policy may be performed on the packets. Performing the at leastone of multiple packet transformation functions specified by the dynamicsecurity policy on the packets may include performing at least onepacket transformation function other than forwarding or dropping thepackets.

In some embodiments, two or more of the packet security gateways may beconfigured in series such that packets forwarded from a first of thepacket security gateways are received by a second of the packet securitygateways. In some embodiments, the dynamic security policy may includetwo rules requiring sequential execution. A first of the packet securitygateways may perform a packet transformation function specified by oneof the rules on the packets and a second of the packet security gatewaysmay subsequently perform a packet transformation function specified bythe other of the rules on packets received from the first packetsecurity gateway.

In some embodiments, the dynamic security policy may include a rulespecifying a set of network addresses for which associated packetsshould be dropped and a rule specifying that all packets associated withnetwork addresses outside the set should be forwarded. Additionally oralternatively, the dynamic security policy may include a rule specifyinga set of network addresses for which associated packets should beforwarded and a rule specifying that all packets associated with networkaddresses outside the set should be dropped. In some embodiments, thesecurity policy management server may receive information associatedwith one or more Voice over Internet Protocol (VoIP) sessions and theset of network addresses for which associated packets should beforwarded may be created or altered utilizing the information associatedwith the one or more VoIP sessions.

In some embodiments, the packet security gateways may receive three ormore dynamic security policies from the security policy managementserver. A first of the dynamic security policies may specify a first setof network addresses for which packets should be forwarded. A second ofthe dynamic security policies may be received after the first and mayspecify a second set of network addresses, which includes more networkaddresses than the first set, for which packets should be forwarded. Athird of the dynamic security policies may be received after the secondand may specify a third set of network addresses, which includes morenetwork addresses than the second set, for which packets should beforwarded.

In some embodiments, the dynamic security policy may include two rulesthat each specify a set of network addresses. The dynamic securitypolicy may specify that packets associated with the first set of networkaddresses should be placed in a first forwarding queue and packetsassociated with the second set of network addresses should be placed ina second forwarding queue. The first forwarding queue may have adifferent queueing policy, for example, a higher forwarding rate, thanthe second forwarding queue.

In some embodiments, the dynamic security policy may include a rulespecifying a set of network addresses and an additional parameter. Thepacket transformation function specified by the dynamic security policymay include routing packets that fall within the specified set and matchthe additional parameter to a network address different from adestination network address specified by the packets. In someembodiments, the additional parameter may be a Session InitiationProtocol (SIP) Uniform Resource Identifier (URI). The network addressdifferent from the destination network address may correspond to adevice configured to copy information contained within the packets andforward the packets to the destination network address specified by thepackets.

In some embodiments, the packet transformation function may forward thepackets into the network protected by the packet security gateway. Insome embodiments, the packet transformation function may forward thepackets out of the network protected by the packet security gateway. Insome embodiments, the packet transformation function may forward the oneor more packets to an IPsec stack having an IPsec security associationcorresponding to the packets. In some embodiments, the packettransformation function may drop the packets.

In some embodiments, the dynamic security policy may include multiplerules. One of the rules may specify the packet transformation function.In some embodiments, one of the rules may specify a five-tuple of valuesselected from packet header information. The five-tuple may specify oneor more protocol types, one or more IP source addresses, one or moresource ports, one or more IP destination addresses, and one or moredestination ports. In some embodiments, one of the rules may specify aDifferentiated Service Code Point (DSCP) that maps to a DSCP field in anIP header of one of the packets.

In some embodiments, one of the packet security gateways may operate ina network layer transparent manner. For example, the packet securitygateway may send and receive traffic at a link layer using an interfacethat is not addressed at the network layer and simultaneously performthe packet transformation function at the network layer. Additionally oralternatively, the packet security gateway may include a managementinterface having a network layer address. Access to the managementinterface may be secured at the application level.

In some embodiments, the dynamic security policy may include a rulegenerated based, at least in part, on a list of known network addressesassociated with malicious network traffic. In some embodiments, the listof known network addresses associated with malicious network traffic maybe received from a subscription service that aggregates informationassociated with malicious network traffic.

In some embodiments, the packets associated with the network protectedby the packet security gateway may originate within the networkprotected by the packet security gateway and may be destined for anetwork distinct from the network protected by the packet securitygateway. Additionally or alternatively, the packets associated with thenetwork protected by the packet security gateway may originate within anetwork distinct from the network protected by the packet securitygateway and may be destined for a host within the network protected bythe packet security gateway.

In some embodiments, one of the packet security gateways may be locatedat each boundary between a protected network associated with thesecurity policy management server and an unprotected network.

Other details and features will be described in the sections thatfollow.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is pointed out with particularity in the appendedclaims. Features of the disclosure will become more apparent upon areview of this disclosure in its entirety, including the drawing figuresprovided herewith.

Some features herein are illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings, in whichlike reference numerals refer to similar elements.

FIG. 1 illustrates an exemplary network environment in which one or moreaspects of the disclosure may be implemented.

FIG. 2 illustrates an exemplary packet security gateway.

FIG. 3 illustrates an exemplary dynamic security policy.

FIG. 4 illustrates an exemplary configuration of multiple packetsecurity gateways in series.

FIG. 5 illustrates an exemplary security policy management server.

FIG. 6 illustrates an exemplary network environment for implementing amonitoring service.

FIG. 7 illustrates an exemplary network environment that includes asecured network having multiple boundaries with unsecured networks.

FIG. 8 illustrates an exemplary network environment that includesmultiple distinct secured networks.

FIG. 9 illustrates an exemplary secure LAN environment.

FIG. 10 illustrates an exemplary method for protecting a securednetwork.

FIG. 11 illustrates an exemplary method for protecting a secured networkthat includes identifying packets based on application-layerpacket-header information.

FIG. 12 illustrates an exemplary method for protecting a secured networkthat includes performing a packet digest logging function on packetsthat correspond to specified packet-identification criteria.

FIG. 13 illustrates an exemplary method for protecting a secured networkthat includes receiving security updates from multiple sources.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized, and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

Various connections between elements are discussed in the followingdescription. These connections are general and, unless specifiedotherwise, may be direct or indirect, wired or wireless. In thisrespect, the specification is not intended to be limiting.

FIG. 1 illustrates an exemplary network environment in which one or moreaspects of the disclosure may be implemented. Referring to FIG. 1,network environment 100 may include networks A-E 102, 104, 106, 108, and110. One or more networks within network environment 100 may be a LocalArea Network (LAN) or a Wide Area Network (WAN). Such a LAN or WAN maybe associated, for example, with an organization (e.g., a company,university, enterprise, or government agency). For example, networks A-D102, 104, 106, and 108 may be LANs, any combination of which may beassociated with one or more organizations. One or more networks withinnetwork environment 100 may interface with one or more other networkswithin network environment 100. For example, network environment 100 mayinclude a WAN that interfaces one or more LANs within networkenvironment 100 or network environment 100 may include one or moreInternet Service Providers (ISPs) that interface one or more LANs orWANs within network environment 100 via the Internet. For example,network E 110 may comprise the Internet and may interface networks A-D102, 104, 106, and 108.

As used herein, a packet security gateway includes any computing deviceconfigured to receive packets and perform a packet transformationfunction on the packets. Optionally, a packet security gateway mayfurther be configured to perform one or more additional functions asdescribed herein. As used herein, a security policy management serverincludes any computing device configured to communicate a dynamicsecurity policy to a packet security gateway. Optionally, a securitypolicy management server may further be configured to perform one ormore additional functions as described herein. As used herein, a dynamicsecurity policy includes any rule, message, instruction, file, datastructure, or the like that specifies criteria corresponding to one ormore packets and identifies a packet transformation function to beperformed on packets corresponding to the specified criteria.Optionally, a dynamic security policy may further specify one or moreadditional parameters as described herein.

Network environment 100 may include one or more packet security gatewaysand one or more security policy management servers. For example, networkenvironment 100 may include packet security gateways 112, 114, 116, and118, and security policy management server 120. One or more securitypolicy management servers may be associated with a protected network.For example, networks A-D 102, 104, 106, and 108 may each be distinctLANs associated with a common organization and may each form part of aprotected network associated with security policy management server 120.Many network protocols route packets dynamically, and thus the path agiven packet may take cannot be readily predicted. Accordingly it may beadvantageous to locate a packet security gateway at each boundarybetween a protected network and an unprotected network. For example,packet security gateway 112 may be located at the boundary betweennetwork A 102 and network E 110. Similarly, packet security gateway 114may be located at the boundary between network B 104 and network E 110;packet security gateway 116 may be located at the boundary betweennetwork C 106 and network E 110; and packet security gateway 118 may belocated at the boundary between network D 108 and network E 110. As willbe described in greater detail below, each of one or more packetsecurity gateways associated with a security policy management servermay be configured to receive a dynamic security policy from the securitypolicy management server, receive packets associated with a networkprotected by the packet security gateway, and perform a packettransformation function specified by the dynamic security policy on thepackets. For example, each of packet security gateways 112, 114, 116,and 118 may be configured to receive a dynamic security policy fromsecurity policy management server 120. Each of packet security gateways112, 114, 116, and 118 may also be configured to receive packetsrespectively associated with networks A-D 102, 104, 106, and 108. Eachof packet security gateways 112, 114, 116, and 118 may further beconfigured to perform a packet transformation function specified by thedynamic security policy received from security policy management server120 on the packets respectively associated with networks A-D 102, 104,106, and 108.

FIG. 2 illustrates an exemplary packet security gateway according to oneor more aspects of the disclosure. Referring to FIG. 2, as indicatedabove, packet security gateway 112 may be located at network boundary200 between network A 102 and network E 110. Packet security gateway 112may include processor 202, memory 204, network interfaces 206 and 208,packet filter 214, and management interface 222. Processor 202, memory204, network interfaces 206 and 208, packet filter 214, and managementinterface 222 may be interconnected via data bus 210. Network interface206 may connect packet security gateway 112 to network E 110. Similarly,network interface 208 may connect packet security gateway 112 to networkA 102. Memory 204 may include one or more program modules that whenexecuted by processor 202, configure packet security gateway 112 toperform various functions as described herein.

Packet security gateway 112 may be configured to receive a dynamicsecurity policy from security policy management server 120. For example,packet security gateway 112 may receive dynamic security policy 212 fromsecurity policy management server 120 via management interface 222(i.e., out-of-band signaling) or network interface 206 (i.e., in-bandsignaling). Packet security gateway 112 may include one or more packetfilters or packet discriminators, or logic for implementing one or morepacket filters or packet discriminators. For example, packet securitygateway 112 may include packet filter 214, which may be configured toexamine information associated with packets received by packet securitygateway 112 and forward the packets to one or more packet transformationfunctions based on the examined information. For example, packet filter214 may examine information associated with packets received by packetsecurity gateway 112 (e.g., packets received from network E 110 viamanagement interface 222 or network interface 206) and forward thepackets to one or more of packet transformation functions 1-N 216, 218,and 220 based on the examined information.

As will be described in greater detail below, dynamic security policy212 may include one or more rules and the configuration of packet filter214 may be based on one or more of the rules included in dynamicsecurity policy 212. For example, dynamic security policy 212 mayinclude one or more rules specifying that packets having specifiedinformation should be forwarded to packet transformation function 216,while all other packets should be forwarded to packet transformationfunction 218. Packet transformation functions 1-N 216, 218, and 220 maybe configured to perform one or more functions on packets they receivefrom packet filter 214. For example, packet transformation functions 1-N216, 218, and 220 may be configured to forward packets received frompacket filter 214 into network A 102, forward packets received frompacket filter 214 to an IPsec stack having an IPsec security associationcorresponding to the packets, or drop packets received from packetfilter 214. In some embodiments, one or more of packet transformationfunctions 1-N 216, 218, and 220 may be configured to drop packets bysending the packets to a local “infinite sink” (e.g., the/dev/nulldevice file in a UNIX/LINUX system).

In some embodiments, packet security gateway 112 may be configured in anetwork layer transparent manner. For example, packet security gateway112 may be configured to utilize one or more of network interfaces 206and 208 to send and receive traffic at the link layer. One or more ofnetwork interfaces 206 and 208, however, may not be addressed at thenetwork layer. Because packet filter 214 and packet transformationfunctions 1-N 216, 218, and 220 operate at the network layer, PSG 112may still perform packet transformation functions at the network layer.By operating in a network layer transparent manner, packet securitygateway 112 may insulate itself from network attacks (e.g., DDoSattacks) launched at the network layer because attack packets cannot berouted to the network interfaces 206 and 208. In some embodiments,packet security gateway 112 may include management interface 222.Management interface 222 may be addressed at the network level in orderto provide packet security gateway 112 with network leveladdressability. Access to management interface 222 may be secured, forexample, at the application level by using a service such as SSH, orsecured at the transport level using, e.g., TLS, or secured at thenetwork level by attaching it to a network with a separate address spaceand routing policy from network A 102 and network E 110, or secured atthe link level, e.g., using the IEEE 802.1X framework, etc.

The flows illustrated by FIG. 2 are merely exemplary and show packetsthat originate within a network distinct from network A 102 and aredestined for a host within network A 102 in order to simplify theillustration. Packet security gateway 112 may be configured to receiveand filter packets that originate within a network other than network A102 (e.g., networks B-E 104, 106, 108, or 110) and are destined for ahost within network A 102, as well as packets that originate withinnetwork A 102 destined for a network distinct from network A 102 (e.g.,network B-D 104, 106, 108, or 110). That is, packet security gateway 112may be configured to filter and perform one or more packettransformation functions on packets flowing in either direction and maythus be utilized, for example, to both protect network A 102 frommalicious network traffic and to prevent malicious network traffic fromleaving network A 102.

FIG. 3 illustrates an exemplary dynamic security policy in accordancewith one or more embodiments. Referring to FIG. 3, dynamic securitypolicy 300 may include rules 1-5 302, 304, 306, 308, and 310. Each rulemay specify criteria and one or more packet transformation functionsthat should be performed for packets associated with the specifiedcriteria. The specified criteria may take the form of a five-tuple ofvalues selected from packet header information, specifying a protocoltype of the data section of the IP packet (e.g., TCP, UDP, ICMP, or anyother protocol), one or more source IP addresses, one or more sourceport values, one or more destination IP addresses, and one or moredestination ports. For example, rule 1 302 may specify that IP packetscontaining TCP packets, originating from a source IP address that beginswith 140, having any source port, destined for an IP address that beginswith 130, and destined for port 20 should have an accept packettransformation function (e.g., the identity function) performed on them.Similarly, rule 2 304 may specify that IP packets containing TCPpackets, originating from a source IP address that begins with 140,having any source port, destined for any IP address, and destined forport 80 should have an accept packet transformation function performedon them; rule 3 306 may specify that IP packets containing TCP packets,originating from a source IP address that begins with 150, having anysource port, destined for any IP address that begins with 120, anddestined for port 90 should have an accept packet transformationfunction performed on them; rule 4 308 may specify that IP packetscontaining UDP packets, originating from a source IP address that beginswith 150, having any source port, destined for any IP address, anddestined for port 3030 should have an accept packet transformationfunction performed on them; and rule 5 310 may specify that IP packetscontaining any data, originating from any source IP address, having anysource port, destined for any IP address, and destined for any portshould have a deny packet transformation function performed on them. Oneor more rules included in dynamic security policy 300 may be specifiedin IP version 4 or IP version 6. In some embodiments, the specifiedcriteria may comprise values selected from application-layerpacket-header information. For example, application-layer hypertexttransfer protocol (HTTP) packets, which transfer information betweeninstances of web client applications (e.g., web browsers) and web serverapplications (e.g., named web sites such as www.examplewebsite.com), maycontain headers that specify methods and/or one or more uniform resourceidentifiers (URIs) for transferring resources (e.g., files) betweenclient and servers. For example, the HTTP GET method may transferURI-labeled resources (e.g., hypertext markup language (HTML) files)from a server to a client. Similarly, the HTTP PUT method may transferresources from a client to a server. A rule may specify that IP packetscontaining HTTP packets with a GET method and transferring a resourcewith a particular URI should have an accept packet transformationfunction performed on them. Another rule may specify that IP packetscontaining HTTP packets with a PUT method and transferring a resource toa server with a particular URI should have a deny packet transformationfunction performed on them. Rules may specify criteria comprising valuesselected from five-tuple header information and/or values selected fromapplication-layer header information.

As will be described in greater detail below, dynamic security policy300 may include one or more rules that specify a packet transformationfunction other than forwarding (accepting or allowing) or dropping(denying) a packet. For example, rule 3 306 may specify that IP packetscontaining TCP packets, originating from a source IP address that beginswith 150, having any source port, destined for any IP address thatbegins with 120, and destined for port 90 should not only have an acceptpacket transformation function performed on them, but should also berouted to a monitoring device.

One or more rules within dynamic security policy 300 may be required toexecute in a specific order. For example, it may be required that rule 5310 be executed last. Because rule 5 310 specifies that any packetshould have a deny packet transformation function performed on it, if itwere executed before a rule specifying an accept packet transformationfunction (e.g., one or more of rules 1-4 302, 304, 306, or 308), nopackets matching the criteria specified by the rule specifying theaccept packet transformation function would pass through a packetsecurity gateway implementing dynamic security policy 300. Similarly,two or more rules within dynamic security policy 300 may specifyoverlapping criteria and different packet transformation functions. Insuch cases, the order-of-application of the rules may determine whichrule is applied to a packet that would match the two or more rules. Suchrules may be merged together or otherwise transformed into a differentset of rules without overlapping criteria, which may produce the sameresult as the original set of rules, when applied to any packet.

A dynamic security policy may utilize the combination of one or morerules to create policies for governing packets within a networkenvironment or effectuating one or more services within a networkenvironment. For example, a dynamic security policy may include one ormore rules, the combination of which may effectuate a blocklist servicewithin a network environment. A dynamic security policy that effectuatesa blocklist service within a network environment may include one or morerules specifying criteria (e.g., a set of network addresses) for whichassociated packets should be blocked, dropped, or denied, and at leastone rule specifying that all packets outside the specified block setsshould be forwarded, accepted, or allowed. Such a dynamic securitypolicy may be constructed by including one or more rules specifyingcriteria (e.g., a set of network addresses) for which associated packetsshould be dropped, and a wildcard rule, designated to be executed last,and specifying that all packets should be allowed. One or more dynamicsecurity policies that effectuate a blocklist service may be utilized toimplement one or more Virtual Private Networks (VPNs).

A dynamic security policy may also include one or more rules, thecombination of which may effectuate an allowlist service within anetwork environment. A dynamic security policy that effectuates anallowlist service within a network environment may include one or morerules specifying criteria (e.g., a set of network addresses) for whichassociated packets should be forwarded, allowed, or accepted, and atleast one rule specifying that all packets outside the specified allowsets should be blocked, denied, or dropped. Such a dynamic securitypolicy may be constructed by including one or more rules specifyingcriteria (e.g., a set of network addresses) for which associated packetsshould be forwarded, and a wildcard rule, designated to be executedlast, and specifying that all packets should be blocked. For example,dynamic security policy 300 includes rules 1-4 302, 304, 306, and 308,each of which specifies a set of network addresses for which packetsshould be allowed, and rule 5 310 which specifies that all packetsshould be dropped. Thus, if rules 1-5 302, 304, 306, 308, and 310 areexecuted in order, dynamic security policy 300 will effectuate anallowlist service.

A dynamic security policy may also include one or more rules, thecombination of which may effectuate a VoIP firewall service within anetwork environment. As will be discussed in greater detail below, asecurity policy management server may receive information associatedwith VoIP sessions. For example, a security policy management server mayreceive information associated with VoIP sessions from one or moresoftswitches (e.g., H.323 softswitches, SIP IP Multimedia Subsystem(IMS) softswitches) or session border controllers when a VoIP session isinitialized or set up. In order to allow packets associated with such aVoIP session within a network protected by one or more packet securitygateways associated with the security policy management server, thesecurity policy management server may utilize the received informationassociated with the VoIP sessions to construct one or more rules forallowing the packets associated with the VoIP session. When the VoIPsession is terminated or torn down, the softswitch or session bordercontroller may notify the security policy management server, which maycreate or alter one or more rules to reflect the termination of the VoIPsession (e.g., to deny future packets which may match criteriapreviously associated with the VoIP session).

A dynamic security policy may also include one or more rules or rulesets, the combination of which may effectuate a phased restorationservice within a network environment. Such a phased restoration servicemay be used in the event of a network attack (e.g., a DDoS attack). Whenan attack occurs a network may be overwhelmed with network traffic andbe unable to route all or any of the traffic. In the event of such anattack, it may be beneficial to utilize a dynamic security policy whicheffectuates a phased restoration service. Such a dynamic security policymay include one or more rules or rule sets configured for execution intime-shifted phases. Each of the rules or rule sets may specifyprogressively larger sets of network addresses. For example, a dynamicsecurity policy may include three rules or rule sets which may beconfigured for execution in time-shifted phases. A first of the rules orrule sets may specify a relatively small set of network addresses forwhich packets should be forwarded (e.g., network addresses correspondingto mission critical network devices). A second of the rules or rule setsmay specify a relatively larger set of network addresses for whichpackets should be forwarded (e.g., network addresses corresponding totrusted network devices). A third of the rules or rule sets may specifyan even larger set of network addresses for which packets should beforwarded (e.g., network addresses corresponding to all network devicesthat would be allowed under ordinary circumstances). The dynamicsecurity policy may specify that the rules or rule sets should beimplemented in time-shifted phases. That is, the dynamic security policymay specify that the first rule or rule set should be executed first,and that the second rule or rule set should be executed at a time afterthe time at which the first rule or rule set is executed, and the thirdrule or rule set should be executed at a time after the time at whichthe second rule or rule set is executed. Such a dynamic security policymay assist a network in recovering from an attack, by allowing thenetwork to isolate itself from the attack or recover in a controlledmanner.

A dynamic security policy may also include one or more rules, thecombination of which may effectuate an enqueueing service within anetwork environment. A dynamic security policy that effectuates anenqueueing service may include one or more rules that specify sets ofnetwork addresses and packet transformation functions that queue packetsin one or more queues corresponding to the sets. These queues may thenbe serviced at varying rates. For example, a dynamic security policy mayinclude two rules, each of which specify a set of network addresses. Afirst of the rules may specify that packets corresponding to itsspecified set should be queued in a first forwarding queue. A second ofthe rules may specify that packets corresponding to its specified setshould be queued in a second forwarding queue. The first forwardingqueue may be serviced at a higher forwarding rate than the secondforwarding queue. Such an enqueueing service may be utilized during orfollowing a network attack, or generally to provide prioritized serviceto critical network devices (e.g., when network resources are strained).In some embodiments, one or more rules contained within a dynamicsecurity policy may include an arbitrary selector which may correspondto one or more parameters or fields associated with a packet. Forexample, a dynamic security policy rule may include a DifferentiatedService Code Point (DSCP) selector that corresponds to a DSCP field inan IP header. Thus, two packets having different values within thespecified DSCP field may correspond to two distinct rules within adynamic security policy and have different packet transformationfunctions performed on them. For example, two otherwise identicalpackets having different values within the specified DSCP field may bequeued in two different forwarding queues that have different forwardingrates, and may thus receive differentiated service.

A dynamic security policy may also include one or more rules, thecombination of which may effectuate a multi-dimensional routing serviceor a multi-dimensional switching service within a network environment.For example, in some embodiments, a dynamic security policy may includeone or more rules that specify a set of network addresses and anadditional parameter. Such rules may further specify a packettransformation function configured to route packets within the specifiedset of network addresses that match the additional parameter to anetwork address distinct from the packets' respective destinationnetwork addresses. For example, the packet transformation function maybe configured to encapsulate such packets (e.g., as described byInternet Engineering Task Force (IETF) Request For Comment (RFC) 2003)with an IP header specifying a network address different from theirrespective destination addresses. The packets may then be routed to thenetwork address specified by the encapsulating IP header, which maycorrespond to a network device configured to utilize such packets ordata contained within them, strip the IP header from the packets, andforward the packets to their respective destination addresses. In someembodiments, the packet transformation function may be configured toalter or modify the destination address of the packets, which may thenbe routed to the altered or modified destination address. Additionallyor alternatively, the packet transformation function may be configuredto assign such packets to a particular Layer-2 VLAN (e.g., as describedby IEEE 802.1Q). The packets may then be switched to another device onthe same VLAN, which may or may not be on the IP-layer path that thepacket would have taken if it were routed according to the packet'sdestination IP address instead of being switched through the VLAN.

As will be described in greater detail below, in some embodiments adynamic security policy may include one or more rules, the combinationof which may effectuate an implementation of a multi-dimensional routingservice for performing a monitoring service within a networkenvironment. For example, a dynamic security policy may include one ormore rules that specify a set of network addresses (e.g., a set ofnetwork addresses from which a call that is to be monitored is expectedto originate within) and an additional parameter (e.g., a SIP URIcorresponding to a caller to be monitored). As indicated above, suchrules may further specify a packet transformation function configured toroute or switch packets within the specified set of network addressesthat match the additional parameter (e.g., the SIP URI) to a networkaddress corresponding to a monitoring device. The network addresscorresponding to the monitoring device may be different from thepackets' destination network address (e.g., an address corresponding tothe called party or a softswitch associated with the called party). Forexample, the packet transformation function may be configured toencapsulate the packets with an IP header specifying the network addresscorresponding to the monitoring device. The packets may then be routed(or rerouted) to the monitoring device, which may be configured to copythe packets or data contained within them (e.g., for subsequent reviewby a law enforcement or national security authority), strip the IPheader from them, and then forward the packets to their destinationaddress (e.g., the address corresponding to the called party orsoftswitch associated with the called party).

In some embodiments, a dynamic security policy may include one or morerules, the combination of which may effectuate an implementation of aninformational service for performing a network communications awarenessservice, a network security awareness service, and/or a network threatawareness service (e.g., for a particular network environment). Forexample, a dynamic security policy may include one or more rules thatspecify criteria such as one or more network addresses, protocol types,method types, and/or directions (e.g., inbound, outbound, or the like)that are indicative of packet communications that are of interest to anorganization that operates the secured network. Such rules may furtherspecify a packet transformation function that, when applied to a packetthat matches such a rule, produces a digest version, or log, of thepacket. This packet log (or digest) may contain selected packetinformation and/or system information (e.g., associated networkaddresses, ports, protocol types, URIs, arrival times, packet sizes,directions, interface names, media access control (MAC) addresses,matching rule IDs, metadata associated with matching rules, enforcedpolicy names, or the like). The associated packet security gateway maystore and/or forward packet logs using a logging system based on astandard (e.g., syslog, or the like). Awareness application servers mayread packet logs and perform various transformations on the logs toproduce awareness information, which may be accessed by clientapplications.

As indicated above, a significant challenge associated with building ascalable proactive solution for protecting a secured network, is theneed to filter substantially all network traffic at a high resolution.Filtering traffic at a high resolution often requires the use of manyrules. In a large network, where traffic volumes may be enormous, thetime required to provide high resolution filtering (e.g., the timerequired to apply a large number of rules to a large volume of traffic)has traditionally been thought to render proactive network protectionsolutions infeasible. This concern may be particularly acute in networkenvironments that utilize low-latency applications (e.g., VoIP).

Recent advances in packet filtering technology have reduced the timerequired to apply large rule sets to network traffic. For example, U.S.Patent Application Publication Nos. 2006/0195896 and 2006/0248580 toFulp et al., and U.S. Patent Application Publication No. 2011/0055916 toAhn, describe advanced packet filtering technologies, and are eachincorporated by reference herein in their entireties.

One approach to providing high resolution filtering, while reducing thenumber of rules applied to network traffic, may be utilized when adynamic security policy is combinatorially complete. For example, adynamic security policy may be configured to allow bi-directionalcommunication between a set of N internal hosts {I₁, I₂, . . . , I_(N)}within a protected network and a set of M external hosts {E₁, E₂, . . ., E_(M)} outside the protected network. To enable communications betweenthe internal hosts and the external hosts, the dynamic security policymay be constructed to include a set of rules containing each possiblecombination of internal hosts and external hosts (e.g., {{I₁, E₁}, {I₁,E₂}, . . . {I₁, E_(M)}, {I₂, E₁}, {I₂, E₂}, . . . {I₂, E_(M)}, . . .{I_(N), E₁}, {I_(N), E₂}, . . . {I_(N), E_(M)}}), each of the rulesbeing associated with an allow packet transformation function. Such adynamic security policy would have N*M rules for allowing communicationbetween the internal hosts and the external hosts that originate fromone of the internal hosts and are destined for one of the externalhosts, and an additional N*M rules for allowing communications betweenthe internal hosts and the external hosts that originate from one of theexternal hosts and are destined for one of the internal hosts. Anequivalent result may be achieved, however, by constructing two smallerdynamic security policies: a first dynamic security policy that includesrules specifying the N internal hosts (e.g., {{I₁}, {I₂}, . . . ,{I_(N)}}), each rule being associated with an accept packettransformation function; and a second dynamic security policy thatincludes rules specifying the M external hosts (e.g., {{E₁}, {E₂}, . . ., {E_(M)}}), each rule being associated with an accept packettransformation function. Such a construct of dynamic security policiesmay be implemented using a system of packet security gateways configuredin series.

FIG. 4 illustrates an exemplary configuration of multiple packetsecurity gateways connected in series. Referring to FIG. 4, packetsecurity gateway 112 may include one or more packet security gatewaysconfigured in series. For example, packet security gateway 112 mayinclude packet security gateways 1-N 400, 402, and 404. Packet securitygateways 1-N 400, 402, and 404 may be configured so that packetsforwarded by packet security gateway 1 400 are received by packetsecurity gateway 2 402, and packets forwarded by packet security gateway2 402 are received by the next packet security gateway in the series,all the way through packet security gateway N 404. Each of packetsecurity gateways 1-N 400, 402, and 404 may include a packet filter,similar to packet filter 214 described above with respect to FIG. 2, andone or more packet transformation functions, similar to packettransformation functions 1-N 216, 218, and 220 described above withrespect to FIG. 2. Packet security gateways 1-N 400, 402, and 404 may beutilized to implement a construct of dynamic security policies similarto that described above.

For example, packet security gateway 1 400 may be configured toimplement P₁, which may include rules specifying M external hosts (e.g.,{{E₁}, {E₂}, . . . , {E_(M)}}), each rule being associated with anaccept packet transformation function. Packet security gateway 2 402 maybe configured to implement P₂, which may include rules specifying Ninternal hosts (e.g., {{I₁}, {I₂}, . . . , {I_(N)}}), each rule beingassociated with an accept packet transformation function. A packetreceived by packet security gateway 112 may be initially received viapacket security gateway 1 400's network interface. Packet securitygateway 1 400 may apply one or more of the rules in P₁ to the receivedpacket until the packet matches criteria specified by a rule in P₁, atwhich point packet security gateway 1 400 may perform a packettransformation function specified by the rule on the packet. Forexample, a packet may be received by packet security gateway 112 thatoriginates from external host E₅ (e.g., a host within network E 110) andis destined for internal host I₇ (e.g., a host within network A 102).Packet security gateway 1 400 may apply one or more of the rules in P₁(e.g., {{E₁}, {E₂}, . . . , {E_(M)}}) to the received packet and thereceived packet may match the criteria specified by one of the rules inP₁ (e.g., {{E₅}). The rule may specify that an accept packettransformation function should be performed, and packet security gateway1 400 may utilize one or more of its packet transformation functions toperform the accept packet transformation function on the packet andforward the packet to packet security gateway 2 402. Packet securitygateway 2 402 may apply one or more of the rules in P₂ (e.g., {{I₁},{I₂}, . . . , {I_(N)}}) to the packet and the packet may match thecriteria specified by one of the rules in P₂ (e.g., {{I₇}). The rule mayspecify that an accept packet transformation function should beperformed, and packet security gateway 2 402 may utilize one or more ofits packet transformation functions to perform the accept packettransformation function on the packet and forward the packet to networkA 102.

It will be appreciated that utilizing multiple packet security gatewaysin series to implement dynamic security policy constructs may increaseperformance and decrease memory resource requirements. For example, inthe described scenario packet security gateway 1 400 may have only beenrequired to compare the packet to five rules and packet security gateway2 402 may have only been required to compare the packet to seven rules.In a worst case scenario, packet security gateway 1 400 may have onlybeen required to compare the packet to M rules and packet securitygateway 2 402 may have only been required to compare the packet to Nrules. Moreover, the series configuration may enable packet securitygateway 1 400 to begin implementing P₁ with respect to a subsequentlyreceived packet, while packet security gateway 2 402 simultaneouslyimplements P₂ with respect to the packet forwarded by packet securitygateway 1 400. Furthermore, the memory requirements for this scenariowith packet security gateways in series may be comparable to M+N,whereas originally the combinatorially complete set of rules containedin a single packet security gateway may have required memory comparableto N*M.

FIG. 5 illustrates an exemplary security policy management server.Referring to FIG. 5, security policy management server 120 may includeprocessor 500, memory 502, and network interface 504. One or more ofprocessor 500, memory 502, and network interface 504 may beinterconnected via data bus 506. Network interface 504 may interfacesecurity policy management server 120 with network E 110. Memory 502 mayinclude one or more program modules that when executed by processor 500,configure security policy management server 120 to perform functionsdescribed herein. It will be appreciated that as used herein the term“server” designates one or more computing devices configured to performone or more functions described herein. The term “server” should not beconstrued to imply that a client/server relationship (e.g., arelationship in which a request is received from a client and thenserviced by a server) necessarily exists.

Security policy management server 120 may be configured to communicateone or more dynamic security policies to one or more packet securitygateways within network environment 100. For example, security policymanagement server 120 may communicate one or more dynamic securitypolicies stored in memory 502 to one or more of packet security gateways112, 114, 116, and 118. For example, security policy management server120 may be configured to communicate one or more dynamic securitypolicies to one or more of packet security gateways 112, 114, 116, and118 on a periodic basis, under specified network conditions, wheneversecurity policy management server 120 receives a new dynamic securitypolicy, whenever a dynamic security policy stored on security policymanagement server 120 is changed or altered, or in response to a requestfrom one or more of packet security gateways 112, 114, 116, and 118.

Security policy management server 120 may also be configured to provideone or more administrators associated with security policy managementserver 120 with management interface 510. For example, security policymanagement server 120 may be configured to provide one or moreadministrators with a Graphical User Interface (GUI) or Command LineInterface (CLI). An administrator of security policy management server120 may utilize security policy management server 120's managementinterface 510 to configure security policy management server 120. Forexample, an administrator may configure security policy managementserver 120 in order to associate security policy management server 120with one or more of packet security gateways 112, 114, 116, and 118. Anadministrator of security policy management server 120 may also utilizesecurity policy management server 120's management interface 510 toconstruct one or more dynamic security policies or to load one or moredynamic security policies into security policy management server 120'smemory 502. For example, an administrator associated with securitypolicy management server 120 may manually construct one or more dynamicsecurity policies offline and then utilize security policy managementserver 120's management interface 510 to load such dynamic securitypolicies into security policy management server 120's memory 502.

In some embodiments, security policy management server 120 may beconfigured to add, remove, or alter one or more dynamic securitypolicies stored in memory 502 based on information received from one ormore devices within network environment 100. For example, securitypolicy management server 120's memory 502 may include a dynamic securitypolicy having one or more rules that specify a list of network addressesknown to be associated with malicious network traffic. Security policymanagement server 120 may be configured to automatically create or alterone or more of such rules as new network addresses associated withmalicious network traffic are determined. For example, security policymanagement server 120 may receive updates (e.g. as part of asubscription) from malicious host tracker service 508. Malicious hosttracker service 508 may aggregate information associated with maliciousnetwork traffic and updates received from malicious host tracker service508 may include one or more network addresses that have been determinedto be associated with malicious network traffic. Security policymanagement server 120 may be configured to create or alter one or morerules included within a dynamic security policy associated withmalicious host tracker service 508 to block traffic associated with thenetwork addresses received from malicious host tracker service 508.Additionally or alternatively, as indicated above, security policymanagement server 120 may be configured to create or alter one or moredynamic security policies, or one or more rules included in one or moredynamic security policies, to account for VoIP sessions being initiatedor terminated by a network device within network environment 100.

In some embodiments, security policy management server 120 may beconfigured to add, remove, and/or alter one or more dynamic securitypolicies stored in memory 502 based on information received from two ormore devices within network environment 100. For example, securitypolicy management server 120 may receive updates (e.g., as part of asubscription) from malicious host tracker service 508 and/or one or moreother services. The updates from the two or more services may becorrelated (e.g., by security policy management server 120). Forexample, a network address received from host tracker service 508 may bea duplicate of a network address received from another (e.g., different)service (e.g., a range of network addresses received from host trackerservice 508 may overlap with a range of network addresses received fromanother service). Security policy management server 120 may combine therules associated with these correlated updates from two or more serviceswithin one or more dynamic security policies. Security policy managementserver 120 may be configured to reduce the size of and/or tode-correlate dynamic security policies (e.g., because the performance ofa packet security gateway may be dependent on the size of and/orcorrelations within dynamic security policies). For example, duplicatenetwork addresses may be removed, and/or overlapping ranges of networkaddresses may be combined into one or more new network address ranges.

As indicated above, a dynamic security policy may include one or morerules, the combination of which may effectuate an implementation of amulti-dimensional routing service for performing a monitoring servicewithin a network environment. FIG. 6 illustrates an exemplary networkenvironment for implementing a monitoring service in accordance with oneor more embodiments. Referring to FIG. 6, a user of network environment100 (e.g., a law enforcement or national security authority) may desireto obtain a copy of packets associated with one or more VoIP sessions(e.g., sessions associated with SIP URI exampleuser@exampledomain.com)within network environment 100. Because many SIP-signaled services aredesigned to address sessions dynamically, it may not be possible todetermine, prior to a session being set up, a particular network addressand port from which packets should be copied. Moreover, due to privacyconcerns, regulators may require that only packets associated with thespecified VoIP sessions (e.g., sessions associated with SIP URIexampleuser@exampledomain.com) be copied.

For example, a user associated with SIP URIexampleuser@exampledomain.com may utilize User Equipment (UE) 600 withinnetwork A 102 to place a VoIP call to a user utilizing UE 602 withinnetwork B 104. SIP switch 604 may be utilized by an operator of networkA 102 for switching SIP signals within network A 102. Similarly, SIPswitch 606 may be utilized by an operator of network B 104 for switchingSIP signals within network B 104. One or more of SIP switches 604 and606 may include an analysis application configured to monitor SIPsignals and publish SIP messages associated with specified users to oneor more subscribers. For example, the operator of network A 102 may haveinstalled analysis application 610 on SIP switch 604 (e.g., accessed viaa SIP IMS Service Control (ISC) interface associated with SIP switch604) and configured analysis application 610 to search for and publishSIP messages associated with SIP URI exampleuser@exampledomain.com tosecurity policy management server 120. Similarly, the operator ofnetwork B 104 may have installed analysis application 612 on SIP switch606 and configured analysis application 612 to publish SIP messagesassociated with SIP URI exampleuser@exampledomain.com to security policymanagement server 120.

When the user associated with SIP URI exampleuser@exampledomain.comutilizes UE 600 to place a VoIP call to the user utilizing UE 602,analysis application 610 may detect one or more SIP signaling messagesassociated with the call (e.g., SIP signaling messages for setting upthe call) and publish the messages to security policy management server120. Security policy management server 120 may extract one or morenetwork addresses and port numbers from the SIP signaling messages(e.g., a network address and port number utilized by UE 600 for placingthe VoIP call to UE 602). Security policy management server 120 mayutilize the extracted network addresses and port numbers to create a newdynamic security policy or alter one or more rules within an existingdynamic security policy. For example, security policy management server120 may construct a new dynamic security policy that includes a rulespecifying one of the extracted network addresses and port numbers, aswell as a packet transformation function configured to route associatedpackets to monitoring device 608. Security policy management server 120may communicate the new or modified dynamic security policy to packetsecurity gateway 112.

When packets associated with the VoIP call between UE 600 and UE 602 arereceived by packet security gateway 112, packet filter 214 may identifythe packets as matching the criteria specified by the dynamic securitypolicy received from security policy management server 120 (e.g.,packets addressed to or from the extracted address and port number) andmay perform the packet transformation function configured to route thepackets to monitoring device 608. For example, the packet transformationfunction configured to route the packets to monitoring device 608 may bepacket transformation function 2 218. When packet transformationfunction 2 218 receives the packets from packet filter 214, it mayencapsulate them with an IP header having an address corresponding tomonitoring device 608 and may then forward them to network E 110. Onceforwarded, the packets may be routed based on the address specified bythe encapsulating header, and may thus be communicated to monitoringdevice 608. When the packets are received by monitoring device 608,monitoring device 608 may copy the packets or data contained withinthem, and strip the encapsulating header from them. Monitoring device608 may then forward the packets, without the encapsulating header, tonetwork E 110. Network E 110 may receive the packets forwarded bymonitoring device 608 and may route them based on their destinationaddress (e.g., to UE 602).

In some embodiments, packet security gateway 112 may be configured toperform multiple packet transformation functions on the packetsassociated with the VoIP call between UEs 600 and 602. For example,packet filter 214 may identify the packets as matching the criteriaspecified by the dynamic security policy received from security policymanagement server 120 and may forward the packets to packettransformation functions 1 216 and 2 218. Packet transformation function1 216 may be configured to forward the packets to their destinationaddress (e.g., to UE 602) and packet transformation function 2 218 maybe configured to encapsulate the packets (or a copy of the packets) withan IP header having an address corresponding to monitoring device 608and then forward the encapsulated packets to network E 110. Onceforwarded, the encapsulated packets may be routed based on the addressspecified by the encapsulating header, and may thus be communicated tomonitoring device 608, which may store the packets or data containedwithin them for subsequent review or analysis (e.g., by a lawenforcement or national security authority). In such embodiments, it maynot be necessary for monitoring device 608 to strip the encapsulatingheader from the packets or route them based on their destination address(e.g., to UE 602) because packet transformation function 1 216 may havealready forwarded the packets to their destination address (e.g., to UE602).

It will be appreciated that SIP switch 604's analysis application 610may similarly detect SIP signaling associated with the termination ofthe VoIP call between UE 600 and UE 602 and may publish the SIP messagesto security policy management server 120. Security policy managementserver 120 may utilize one or more network addresses and port numberswithin the messages to construct a new dynamic security policy or modifyone or more rules within an existing dynamic security policy andcommunicate the new or modified dynamic security policy to packetsecurity gateway 112 in order to ensure that future packets associatedwith the network address and port number but not associated with SIP URIexampleuser@exampledomain.com are not routed to monitoring device 608.Security policy management server 120 may communicate any dynamicsecurity policy constructed or modified based on SIP messages to any ofmultiple packet security gateways (e.g., packet security gateways 114and 116) within network environment 100 in order to ensure that allpackets associated with the VoIP call between UE 600 and UE 602 areforwarded to monitoring device 608.

FIG. 7 illustrates an exemplary network environment that includes asecured network having multiple boundaries with unsecured networks inwhich one or more embodiments may be implemented. Network environment700 may include networks A-C 702, 704, and 706.

Networks A 702 and B 704 may be a LAN or WAN associated with anorganization (e.g., a company, university, enterprise, or governmentagency). One or more networks within network environment 700 mayinterface with one or more other networks within network environment700. For example, the organizations associated with networks A 702 and B704 may subscribe to an ISP to provide interconnectivity between theirrespective networks or allow public access to their respective networks(e.g., via the Internet). Each of networks A 702 and B 704 may beconnected to network C 706, which may be the ISP's network. The ISP maydesire to offer an interconnection service between networks A 702 and B704, but may also want to enforce one or more dynamic security policieswith respect to traffic traversing network C 706. Accordingly, one ormore packet security gateways may be located at each boundary betweennetwork A 702 and network C 706, and each boundary between network B 704and network C 706. For example, packet security gateway 708 and packetsecurity gateway 710 may be respectively located at first and secondboundaries between networks A 702 and C 706. Similarly, packet securitygateways 712 and 714 may be respectively located at first and secondboundaries between networks B 704 and C 706. Each of packet securitygateways 708, 710, 712, and 714 may be associated with security policymanagement server 716.

Security policy management server 716 may maintain one or more dynamicsecurity policies configured for protecting network C 706, and may bemanaged by the ISP associated with network C 706. Security policymanagement server 716 may ensure that each of packet security gateways708, 710, 712, and 714 protect each of their respective boundaries withnetwork C 706 in a uniform manner. For example, security policymanagement server 716 may be configured to communicate one or moredynamic security policies it maintains to each of packet securitygateways 708, 710, 712, and 714 on a periodic basis, in response tobeing directed to by a network operator associated with networkenvironment 700, in response to detected network conditions (e.g., anattack or high resource utilization), or in response to a request fromone or more of packet security gateways 708, 710, 712, or 714.

In some embodiments, security policy management server 716 may beconfigured to communicate different dynamic security policies to one ormore of packet security gateways 708, 710, 712, and 714 based on, forexample, their respective locations within network environment 700. Forexample, security policy management server 716 may be configured toimplement one or more anti-spoofing techniques (e.g., ingress filteringor Best Current Practice (BCP) 38, as described by Internet EngineeringTask Force (IETF) Request For Comment (RFC) 2827) with respect tonetwork environment 700. Effective implementation of such techniques mayrequire that a dynamic security policy be based on the location at whichit is being implemented. For example, a dynamic security policy thatimplements ingress filtering may comprise one or more rules that filterbased on a packet's source address, identifying packets having sourceaddresses that could not possibly have originated from a networkdownstream of the ingress filtering point (e.g., packets having spoofedsource addresses). Such rules may vary depending on the boundary pointfor which they are implemented (e.g., a packet for one boundary may beproperly identified as spoofed, yet a packet having the same sourceaddress may be legitimate traffic at a different boundary point).Accordingly, security policy management server 716 may be configured tocommunicate different dynamic security policies to one or more of packetsecurity gateways 708, 710, 712, and 714 based on their respectivelocations within network environment 700. For example, security policymanagement server 716 may communicate a dynamic security policy topacket security gateways 708 and 710 that includes one or more rules forperforming ingress filtering for network A 702 (e.g., for identifyingpackets having source addresses that could not have originated withinnetwork A 702) and a different dynamic security policy to packetsecurity gateways 712 and 714 that includes one or more rules forperforming ingress filtering for network B 704 (e.g., for identifyingpackets having source addresses that could not have originated withinnetwork B 704).

It will be appreciated that by maintaining uniform dynamic securitypolicies at each boundary between networks A 702 and C 706, as well asat each boundary between networks B 704 and C 706, security policymanagement server 716 and packet security gateways 708, 710, 712, and714 may aid the ISP associated with network C 706 in protecting networkC 706 from network attacks.

FIG. 8 illustrates an exemplary network environment that includesmultiple distinct secured networks in which one or more embodiments maybe implemented. Referring to FIG. 8, network environment 800 may includenetworks A 802, B 804, and C 806. Each of networks A 802 and B 804 mayinterface with network C 806 at multiple boundaries within networkenvironment 800. Packet security gateways 808 and 810 may berespectively located at first and second boundaries between networks A802 and C 806. Similarly, packet security gateways 812 and 814 may berespectively located at first and second boundaries between networks B804 and C 806.

Network A 802 and B 804 may both be associated with a commonorganization (e.g., a company, university, enterprise, or governmentagency), or may each be associated with a distinct organization. In theformer case, the common organization may desire to utilize one or moredynamic security policies with respect to network A 802 and one or moredifferent dynamic security policies with respect to network B 804. Inthe latter case, an organization associated with network A 802 maydesire to utilize one or more dynamic security policies with respect tonetwork A 802 and a different organization associated with network B 804may desire to utilize one or more different dynamic security policieswith respect to network B 804. Network environment 800 may includesecurity policy management servers A 816 and B 818. Security policymanagement server A 816 may be associated with network A 802 and maymaintain one or more dynamic security policies configured for protectingnetwork A 802. Similarly, security policy management server B 818 may beassociated with network B 804 and may maintain one or more dynamicsecurity policies configured for protecting network B 804.

Packet security gateways 808 and 810 may be associated with securitypolicy management server A 816. Similarly, packet security gateways 812and 814 may be associated with security policy management server B 818.Security policy management server A 816 may ensure that packet securitygateways 808 and 810 protect each of their respective boundaries withnetwork C 806 in a uniform manner. For example, security policymanagement server A 816 may be configured to communicate one or moredynamic security policies it maintains to packet security gateways 808and 810 on a periodic basis, in response to being directed to by anetwork operator associated with network A 802, in response to detectednetwork conditions (e.g., an attack or high resource utilization), or inresponse to a request from packet security gateway 808 or 810.Similarly, security policy management server B 818 may ensure thatpacket security gateways 812 and 814 protect each of their respectiveboundaries with network C 806 in a uniform manner. For example, securitypolicy management server B 818 may be configured to communicate one ormore dynamic security policies it maintains to packet security gateways812 and 814 on a periodic basis, in response to being directed to by anetwork operator associated with network B 804, in response to detectednetwork conditions (e.g., an attack or high resource utilization), or inresponse to a request from packet security gateway 812 or 814. Byutilizing distinct security policy management servers (e.g., securitypolicy management servers A 816 and B 818), one or more operatorsassociated with distinct networks (e.g., networks A 802 and B 804) maymaintain uniform dynamic security policies at each boundary of theirrespective networks, while simultaneously enabling different dynamicsecurity policies to be maintained for each network. Similarly, byutilizing distinct security policy management servers (e.g., securitypolicy management servers A 816 and B 818), one or more operatorsassociated with a single organization that desires to maintain distinctnetworks (e.g., networks A 802 and B 804) may maintain uniform dynamicsecurity policies at each boundary of their distinct networks, whilesimultaneously enabling different dynamic security policies to bemaintained for each network.

FIG. 9 illustrates an exemplary secure LAN environment protected inaccordance with one or more aspects of the disclosure. Referring to FIG.9, network environment 900 may be a LAN, including hosts A 902, B 904,and C 906. It may also include LAN switch 908. LAN switch 908 may beconfigured to switch network traffic (e.g., packets) between one or moreof hosts A 902, B 904, and C 906. For example, LAN switch 908 mayinclude a switching matrix configured to switch packets received fromone or more of hosts A 902, B 904, and C 906 to one or more of hosts A902, B 904, and C 906. LAN switch 908 may be associated with packetsecurity gateway 910, and network environment 900 may include securitypolicy management server 912.

In some embodiments, packet security gateway 910 may be embedded withinLAN switch 908. Alternatively, packet security gateway 910 may be adevice distinct from LAN switch 908, and LAN switch 908 may beconfigured to route network traffic through packet security gateway 910(e.g., by modifying LAN switch 908's switching matrix). Packet securitygateway 910 may be configured to receive one or more dynamic securitypolicies from security policy management server 912. The dynamicsecurity policies received from security policy management server 912may include one or more rules specifying criteria associated with one ormore of hosts A 902, B 904, and C 906, and may further specify one ormore packet transformation functions to be performed on packets matchingthe specified criteria. Packet security gateway 910 may identify packetsmatching one or more of the criteria specified by the rules and mayperform the associated packet transformation functions on the identifiedpackets. By utilizing packet security gateway 910 within networkenvironment 900, an operator of network environment 900 may be able toprotect network environment 900 from network attacks, as well asimplement one or more services (e.g., blocklist service, allowlistservice, VoIP firewall service, phased restoration service, enqueueingservice, multi-dimensional routing service, or monitoring service)within network environment 900. Network environment 900 may includemultiple LAN switches with embedded or associated packet securitygateways, each of the packet security gateways configured to receive oneor more dynamic security policies from security policy management server912.

FIG. 10 illustrates an exemplary method for protecting a secured networkin accordance with one or more embodiments. The steps may be performedat each of one or more packet security gateways associated with asecurity policy management server. For example, each of packet securitygateways 112, 114, 116, and 118 may be associated with security policymanagement server 120, and the steps may be performed at each of packetsecurity gateways 112, 114, 116, and 118. At step 1000, a dynamicsecurity policy is received from the security policy management server.For example, packet security gateway 112 may receive dynamic securitypolicy 300 from security policy management server 120. At step 1002,packets associated with a network protected by each respective packetsecurity gateway are received. For example, packet security gateway 112may receive UDP packets from a device within network E 110 having anaddress that begins with 150 and that are destined for port 3030 of adevice within network A 102. At step 1004, a packet transformationfunction specified by the dynamic security policy is performed on thepackets. For example, rule 308 of dynamic security policy 300 mayspecify that packets using the UDP protocol, coming from a sourceaddress that begins with 150, having any source port, destined for anyaddress, and destined for port 3030 should have an accept packettransformation function performed on them, packet filter 214 mayidentify the UDP packets received from the device within network E 110as matching the criteria specified by rule 308, packet transformationfunction 1 216 may be configured to forward packets, and packet securitygateway 112 may utilize packet transformation function 1 216 to performthe accept packet transformation function specified by rule 308 on theUDP packets received from the device within network E 110.

FIG. 11 illustrates an exemplary method for protecting a secured networkthat includes identifying packets based on application-layerpacket-header information. Referring to FIG. 11, at step 1102, aplurality of packet security gateways associated with a security policymanagement server may receive a dynamic security policy that includes atleast one rule specifying application-layer packet-header informationand a packet transformation function to be performed on packetscomprising the application-layer packet-header information. For example,packet security gateways 112, 114, 116, and 118 may be associated withsecurity policy management server 120 and may receive a dynamic securitypolicy that includes one or more rules specifying application-layerpacket-header information (e.g., information that identifies one or moreHTTP packets) and a packet transformation function to be performed onpackets comprising the application-layer packet-header information(e.g., an accept or deny packet transformation function) from securitypolicy management server 120. At step 1104, a packet security gateway,of the plurality of packet security gateways associated with thesecurity policy management server, may receive packets associated with anetwork protected by the packet security gateway. For example, packetsecurity gateway 112 may receive packets associated with network A 102(e.g., from a computing device located in network A 102, network B 104,network C 106, network D 108, and/or network E 110).

At step 1106, the packet security gateway may identify, from amongst thepackets associated with the network protected by the packet securitygateway, and on a packet-by-packet basis, one or more packets comprisingthe application-layer packet-header information. For example, in someembodiments, the rule(s) specifying the application-layer packet-headerinformation may identify one or more HTTP packets (e.g., one or moreHTTP packets comprising an HTTP GET method call and/or an HTTP PUTmethod call), and packet security gateway 112 may identify, from amongstthe packets associated with network A 112, one or more packetscomprising the application-layer packet-header information. In someembodiments, identifying the packets comprising the application-layerpacket-header information may include the packet security gatewaydetermining that the packets are among the HTTP packets identified bythe rule(s) (e.g., the HTTP GET method call and/or the HTTP PUT methodcall may specify one or more URIs, and packet security gateway 112 maydetermine that the packet(s) originated from and/or are destined for anetwork address corresponding to the URI(s)). At step 1108, the packetsecurity gateway may perform, on a packet-by-packet basis, the packettransformation function on the identified packet(s). For example, if thepacket transformation function is an accept packet transformationfunction, packet security gateway 112 may forward the packet(s) towardtheir respective destinations. Similarly, if the packet transformationfunction is a deny packet transformation function, packet securitygateway 112 may drop the packet(s).

FIG. 12 illustrates an exemplary method for protecting a secured networkthat includes performing a packet digest logging function on packetsthat correspond to specified packet-identification criteria. Referringto FIG. 12, at step 1202, each of a plurality of packet securitygateways associated with a security policy management server may receivea dynamic security policy that includes at least one rule specifyingpacket-identification criteria and a packet transformation functioncomprising a packet digest logging function to be performed on packetscorresponding to the packet-identification criteria from the securitypolicy management server. For example, packet security gateways 112,114, 116, and 118 may be associated with security policy managementserver 120 and may receive a dynamic security policy that includes oneor more rules specifying packet-identification criteria (e.g.,application-layer packet-header information and/or a five-tuplespecifying one or more transport-layer protocols, a range of sourceaddresses, a range of source ports, a range of destination addresses,and a range of destination ports) and a packet transformation functioncomprising a packet digest logging function to be performed on packetscorresponding to the packet-identification criteria from security policymanagement server 120. At step 1204, a packet security gateway, of theplurality of packet security gateways associated with the securitypolicy management server, may receive packets associated with a networkprotected by the packet security gateway. For example, packet securitygateway 112 may receive packets associated with network A 102 (e.g.,from a computing device located in network A 102, network B 104, networkC 106, network D 108, and/or network E 110).

At step 1206, the packet security gateway may identify from amongst thepackets associated with the network protected by the packet securitygateway, and on a packet-by-packet basis, one or more packetscorresponding to the packet-identification criteria. For example, packetsecurity gateway 112 may identify from amongst the packets associatedwith network A 102 one or more packets corresponding to thepacket-identification criteria (e.g., by determining that the packet(s)comprise the specified application-layer packet-header informationand/or correspond to at least one of the specified transport-layerprotocols, have a source address within the specified range of sourceaddresses, have a source port within the specified range of sourceports, have a destination address within the specified range ofdestination addresses, and/or have a destination port within thespecified range of destination ports). At step 1208, the packet securitygateway may perform, on a packet-by-packet basis, the packet digestlogging function on each of the packets corresponding to thepacket-identification criteria. For example, packet security gateway 112may perform the packet digest logging function on each of the identifiedpackets.

In some embodiments, performing the packet digest logging function mayinclude identifying a subset of information specified by the packetdigest logging function (e.g., a portion of data from the packet, asource address of the packet, a source port of the packet, a destinationaddress of the packet, a destination port of the packet, atransport-protocol type of the packet, a uniform resource identifier(URI) from the packet, an arrival time of the packet, a size of thepacket, a flow direction of the packet, an identifier of an interface ofthe packet security gateway that received the packet, and/or one or moremedia access control (MAC) addresses associated with the packet) foreach of the identified packets, and generating a record comprising thesubset of information for each of the identified packets. In someembodiments, packet security gateway 112 may be configured totemporarily store data comprising the subset of information for each ofthe identified packets, and to utilize the stored data to generate amessage comprising the subset of information (or a portion thereof) foreach of the identified packets. In such embodiments, packet securitygateway 112 may communicate the message to a different computing device(e.g., security policy management server 120). In some embodiments, thesubset of information (or a portion thereof) may be reformatted (e.g.,by packet security gateway 112 and/or security policy management server120) in accordance with a logging system standard (e.g., syslog).

FIG. 13 illustrates an exemplary method for protecting a secured networkthat includes receiving security updates from multiple sources.Referring to FIG. 13, at step 1302, a security policy management servermay receive a security update comprising a set of network addresses froma computing device. For example, security policy management server 120may receive a security update comprising a set of network addresses(e.g., {network address A, network address B, and network address C})from malicious host tracker service 508 (or a computing deviceassociated therewith). At step 1304, the security policy managementserver may update one or more rules stored in its memory to include theset of network addresses. For example, security policy management server120 may update one or more rules of dynamic security policy 300 (e.g., arule specifying a deny packet transformation function) to include theset of network addresses (e.g., network addresses A, B, and C). At step1306, the security policy management server may receive a securityupdate comprising a different set of network addresses from a differentcomputing device. For example, security policy management server 120 mayreceive a security update comprising a different set of networkaddresses (e.g., {network address B, network address C, network addressD, and network address E}) from a different computing device (e.g., adifferent computing device associated with malicious host trackerservice 508 or a computing device associated with a malicious hosttracker service different from malicious host tracker service 508).

At step 1308, the security policy management server may determine thatthe different set of network addresses includes at least a portion ofnetwork addresses included in the set of network addresses, and, at step1310, may identify the at least a portion of network addresses includedin the set of network addresses. For example, security policy managementserver 120 may determine that the different set of network address(e.g., {network address B, network address C, network address D, andnetwork address E}) includes at least a portion of network addresses(e.g., network addresses B and C) included in the set of networkaddresses (e.g., {network address A, network address B, and networkaddress C}), and may identify the at least a portion of networkaddresses included in the set of network addresses (e.g., networkaddresses B and C). At step 1312, the security policy management servermay identify at least one of the rules stored in its memory thatspecifies a range of network addresses comprising the at least a portionof network addresses. For example, security policy management server 120may identify the rule(s) of dynamic security policy 300 updated in step1304 (e.g., the rule(s) updated to include network addresses A, B, andC). At step 1314, the security policy management server may update theidentified rule(s) to include one or more other network addressesincluded in the different set of network addresses. For example,security policy management server 120 may update the identified rules ofdynamic security policy 300 to include one or more other networkaddresses included in the different set of network addresses (e.g.,network addresses D and E).

In some embodiments, the security policy management server may identifytwo or more rules that each specify a range of network addressescomprising the at least a portion of network addresses. For example,security policy management server 120 may identify two rules of dynamicsecurity policy 300 that each include the at least a portion of networkaddresses (e.g., a rule that includes network addresses A, B, C, and F,and a rule that includes network addresses A, B, C, and G). In suchembodiments, the security policy management server may combine the twoor more rules into a rule that specifies a range of network addressesthat includes network addresses specified by each of the two or morerules and the one or more other network addresses included in thedifferent set of network addresses. For example, security policymanagement server 120 may combine the two rules of dynamic securitypolicy 300 that each include the at least a portion of network addresses(e.g., the rule that includes network addresses A, B, C, and F, and therule that includes network addresses A, B, C, and G) into a rule thatspecifies a range of network addresses that includes network addressesspecified by each of the two identified rules and the one or more othernetwork addresses included in the different set of network addresses(e.g., a range that includes network addresses A, B, C, D, E, F, and G).

The functions and steps described herein may be embodied incomputer-usable data or computer-executable instructions, such as in oneor more program modules, executed by one or more computers or otherdevices to perform one or more functions described herein. Generally,program modules include routines, programs, objects, components, datastructures, etc. that perform particular tasks or implement particularabstract data types when executed by one or more processors in acomputer or other data processing device. The computer-executableinstructions may be stored on a computer-readable medium such as a harddisk, optical disk, removable storage media, solid state memory, RAM,etc. As will be appreciated, the functionality of the program modulesmay be combined or distributed as desired in various embodiments. Inaddition, the functionality may be embodied in whole or in part infirmware or hardware equivalents, such as integrated circuits,application-specific integrated circuits (ASIC s), field programmablegate arrays (FPGA), and the like. Particular data structures may be usedto more effectively implement one or more aspects of the disclosure, andsuch data structures are contemplated to be within the scope of computerexecutable instructions and computer-usable data described herein.

Although not required, one of ordinary skill in the art will appreciatethat various aspects described herein may be embodied as a method, anapparatus, or as one or more computer-readable media storingcomputer-executable instructions. Accordingly, those aspects may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, an entirely firmware embodiment, or an embodiment combiningsoftware, hardware, and firmware aspects in any combination.

As described herein, the various methods and acts may be operativeacross one or more computing servers and one or more networks. Thefunctionality may be distributed in any manner, or may be located in asingle computing device (e.g., a server, a client computer, etc.).

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one of ordinary skill in the art willappreciate that the steps illustrated in the illustrative figures may beperformed in other than the recited order, and that one or more stepsillustrated may be optional.

1. (canceled)
 2. A method comprising: receiving, by at least one packetsecurity gateway, a plurality of packets associated with a networkprotected by the at least one packet security gateway; identifying, bythe packet security gateway and on a packet-by-packet basis, one or moreof the plurality of packets comprising first packet-identificationcriteria; performing, by the packet security gateway and on apacket-by-packet basis, a packet digest logging function on each of theone or more packets comprising the first packet-identification criteria;and monitoring, on a packet-by-packet basis, one or more packetscomprising the first packet-identification criteria in response to theperforming the packet digest logging function, wherein the packet digestlogging function is performed based on a security policy comprising atleast one rule specifying the first packet-identification criteria, andwherein the performing the packet digest logging function comprises:identifying a subset of information specified by the packet digestlogging function for each of the one or more packets comprising thefirst packet-identification criteria; and generating, for each of theone or more packets comprising the first packet-identification criteria,a record comprising the subset of information specified by the packetdigest logging function.
 3. The method of claim 2, wherein the firstpacket-identification criteria comprise at least one of transport-layerprotocol information, a source address within a specified range ofsource addresses, a source port within a specified range of sourceports, a destination address within a specified range of destinationaddresses, and a destination port within a specified range ofdestination ports.
 4. The method of claim 2, wherein the identifying asubset of information specified by the packet digest logging function,for each of the one or more of the plurality of packets comprising thefirst packet-identification criteria, comprises identifying a least twoof: a portion of payload data from the packet, a source address of thepacket, a source port of the packet, a destination address of thepacket, a destination port of the packet, a transport-protocol type ofthe packet, a uniform resource identifier (URI) from the packet, anarrival time of the packet, a size of the packet, a flow direction ofthe packet, an identifier of an interface of the packet security gatewaythat received the packet, and one or more media access control (MAC)addresses associated with the packet.
 5. The method of claim 2, whereinthe monitoring, on a packet-by-packet basis, one or more packetscomprises: recording, on a packet-by-packet basis, packet header andpayload data of the one or more packets comprising the firstpacket-identification criteria.
 6. The method of claim 5, furthercomprising: encapsulating each of the one or more packets comprising thefirst packet-identification criteria with an Internet Protocol (IP)header specifying a network address corresponding to a monitoringdevice; stripping, by the monitoring device on a packet-by-packet basis,the IP header specifying the network address corresponding to themonitoring device encapsulating the one or more packets comprising thefirst packet-identification criteria; and forwarding, by the monitoringdevice on a packet-by-packet basis, one or more packets comprising thefirst packet-identification criteria toward their respectivedestinations without the IP header specifying the network addresscorresponding to the monitoring device.
 7. The method of claim 2,further comprising: identifying, by the packet security gateway and on apacket-by-packet basis, one or more of the plurality of packetscomprising second packet-identification criteria; and performing, by thepacket security gateway and on a packet-by-packet basis, an acceptpacket transformation function on each of the one or more packetscomprising the second packet-identification criteria, wherein at leastone rule indicates performing the accept packet transformation functionon the packets comprising the second packet-identification criteria, andwherein the performing the accept packet transformation functioncomprises forwarding, by the packet security gateway, each of the one ormore packets comprising the second packet-identification criteria towardtheir respective destinations.
 8. The method of claim 2, furthercomprising: identifying, by the packet security gateway and on apacket-by-packet basis, one or more of the plurality of packetscomprising second packet-identification criteria; and performing, by thepacket security gateway and on a packet-by-packet basis, a deny packettransformation function on each of the one or more packets comprisingthe second packet-identification criteria, wherein at least one ruleindicates performing the deny packet transformation function on thepackets comprising the second packet-identification criteria, andwherein the performing the deny packet transformation function oncomprises dropping, by the packet security gateway, each of the one ormore packets comprising the second packet-identification criteria. 9.The method of claim 2, further comprising: temporarily storing, by thepacket security gateway, subsets of information specified by the packetdigest logging function for each of the one or more of the plurality ofpackets comprising the first packet-identification criteria; generating,by the packet security gateway, a message comprising at least a portionof the subsets of information for each of the one or more of theplurality of packets comprising the first packet-identificationcriteria; and transmitting, by the packet security gateway and to asecurity policy management server, the message to a security policymanagement server.
 10. A method comprising: receiving, by a packetsecurity gateway of a plurality of packet security gateways, packetsassociated with a network protected by the packet security gateway;identifying, by the packet security gateway, from amongst the packetsassociated with the network protected by the packet security gateway,and on a packet-by-packet basis, one or more packets corresponding to afirst packet-identification criteria, wherein the firstpacket-identification criteria comprises a Differentiated Service CodePoint (DSCP) selector; performing, by the packet security gateway and ona packet-by-packet basis, a packet digest logging transformationfunction on each of the one or more packets corresponding to the firstpacket-identification criteria; and monitoring, on a packet-by-packetbasis, one or more packets comprising the first packet-identificationcriteria in response to the performing the packet digest loggingtransformation function, wherein the performing the packet digestlogging transformation function comprises: identifying a subset ofinformation specified by the packet digest logging transformationfunction for each of the one or more packets comprising the firstpacket-identification criteria; and generating, for each of the one ormore packets comprising the first packet-identification criteria, arecord comprising the subset of information specified by the packetdigest logging transformation function.
 11. The method of claim 10,wherein the subset of information comprises at least one of a portion ofdata from the packet, a source address of the packet, a source port ofthe packet, a destination address of the packet, a destination port ofthe packet, a transport-protocol type of the packet, a uniform resourceidentifier (URI) from the packet, an arrival time of the packet, a sizeof the packet, a flow direction of the packet, an identifier of aninterface of the packet security gateway that received the packet, orone or more media access control (MAC) addresses associated with thepacket.
 12. The method of claim 10, further comprising: temporarilystoring, in a memory of the packet security gateway, the subset ofinformation specified by the packet digest logging transformationfunction for each of the one or more packets corresponding to the firstpacket-identification criteria; and generating, by the packet securitygateway, a message comprising the subset of information specified by thepacket digest logging transformation function for each of the one ormore packets corresponding to the first packet-identification criteria.13. The method of claim 10, further comprising: communicating, by thepacket security gateway and to a security policy management server, amessage comprising the subset of information specified by the packetdigest logging transformation function for each of the one or morepackets corresponding to the first packet-identification criteria. 14.The method of claim 10, further comprising: reformatting the subset ofinformation specified by the packet digest logging transformationfunction in accordance with a logging system.
 15. The method of claim10, wherein the first packet-identification criteria comprises afive-tuple specifying one or more transport-layer protocols, a range ofsource addresses, a range of source ports, a range of destinationaddresses, and a range of destination ports, and wherein identifying theone or more packets corresponding to the first packet-identificationcriteria comprises determining by the packet security gateway that eachof the one or more packets corresponding to the firstpacket-identification criteria corresponds to at least one of the one ormore transport-layer protocols, has a source address within the range ofsource addresses, a source port within the range of source ports, adestination address within the range of destination addresses, and adestination port within the range of destination ports.
 16. The methodof claim 15, wherein identifying the one or more packets correspondingto the first packet-identification criteria comprises determining by thepacket security gateway that each of the one or more packetscorresponding to the first packet-identification criteria comprises atleast a portion of the first packet-identification criteria.
 17. Themethod of claim 10, wherein the monitoring, on a packet-by-packet basis,one or more packets comprises: recording, on a packet-by-packet basis,packet header and payload data of the one or more packets comprising thefirst packet-identification criteria.
 18. The method of claim 17,further comprising: encapsulating each of the one or more packetscomprising the first packet-identification criteria with an InternetProtocol (IP) header specifying a network address corresponding to amonitoring device; stripping, by the monitoring device on apacket-by-packet basis, the IP header specifying the network addresscorresponding to the monitoring device encapsulating the one or morepackets comprising the first packet-identification criteria; andforwarding, by the monitoring device on a packet-by-packet basis, one ormore packets comprising the first packet-identification criteria towardtheir respective destinations without the IP header specifying thenetwork address corresponding to the monitoring device.
 19. A methodcomprising: receiving, by at least one packet security gateway, aplurality of packets associated with a network protected by the at leastone packet security gateway; identifying, by the packet security gatewayand on a packet-by-packet basis, a rule corresponding to each of theplurality of packets based on packet-identification criteria associatedwith each or the plurality of packets; and performing, by the packetsecurity gateway and on a packet-by-packet basis, one of a plurality ofpacket transformation functions on each of the plurality of packetsbased on the packet-identification criteria associated with each or theplurality of packets, wherein the packet transformation functionscomprise: a packet digest logging function comprising, on apacket-by-packet basis and for each packet comprising firstpacket-identification criteria, identifying a subset of informationspecified by the packet digest logging function, generating a recordcomprising the subset of information specified by the packet digestlogging function, encapsulating each of the one or more packets with anInternet Protocol (IP) header specifying a network address correspondingto a monitoring device, and routing each of the one or more packets to amonitoring device, an accept packet transformation function comprising,on a packet-by-packet basis and for each packet comprising secondpacket-identification criteria, forwarding, by the packet securitygateway, each of the one or more packets comprising the secondpacket-identification criteria toward their respective destinations, anda deny packet transformation function comprising, on a packet-by-packetbasis and for each packet comprising third packet-identificationcriteria, dropping, by the packet security gateway, each of the one ormore packets comprising the third packet-identification criteria. 20.The method of claim 19, wherein the packet-identification criteriacomprises a five-tuple specifying one or more transport-layer protocols,a range of source addresses, a range of source ports, a range ofdestination addresses, and a range of destination ports, and whereinidentifying the one or more of the plurality of packets corresponding tothe packet-identification criteria comprises determining by the packetsecurity gateway that each of the one or more of the plurality ofpackets corresponding to the packet-identification criteria correspondsto at least one of the one or more transport-layer protocols, has asource address within the range of source addresses, a source portwithin the range of source ports, a destination address within the rangeof destination addresses, and a destination port within the range ofdestination ports.
 21. The method of claim 19, further comprising:receiving, from the packet security gateway and by the monitoring deviceon a packet-by-packet basis, one or more packets comprising the firstpacket-identification criteria in response to the performing the packetdigest logging function; and recording, by the monitoring device on apacket-by-packet basis, packet header and payload data of the one ormore packets comprising the first packet-identification criteria.